BBS Toolkit

home *** CD-ROM | disk | FTP | other *** search

/ BBS Toolkit / BBS Toolkit.iso / rbbs_pc / rbbsv100.zip / RBBSV100.EXE / RBBSVRFY.DOC < prev next >

Wrap

Text File | 1993-05-19 | 58KB | 1,132 lines

╔═════════════════════════════════════════════════╗ ║ RBBS-Verify Version 1.00 ║ ║ Superior Callback Verification Door For RBBS-PC ║ ║ Copyright (C) 1993 By Lightning Software ║ ║ All Rights Reserved Worldwide ║ ║ * Sysop Documentation * ║ ╚═════════════════════════════════════════════════╝ "RBBS-PC: The Best Things in Life Are Still FREE!" [ Written And Coded By Robert L. Folmer ] Table of Contents ───────────────── Shareware Notice.....................................................1 Warranty.............................................................2 Acknowledgements.....................................................3 Introduction (Overview/Summary)......................................4 Introduction (Overview/Summary) (Continued)..........................5 Installing RBBS-Verify...............................................6 Installing RBBS-Verify (Continued)...................................7 Installing RBBS-Verify (Continued)...................................8 Installing RBBS-Verify (Continued)...................................9 Installing RBBS-Verify (Continued)..................................10 Installing RBBS-Verify (Continued)..................................11 Files Included......................................................12 Files Created During Run-Time.......................................13 Optional Files Created During Operation.............................14 Optional Command Line Switches......................................15 Optional Command Line Switches (Continued)..........................16 Sysop Function/ALT Keys.............................................17 Using RBBS-Verify on Non-RBBS Systems...............................18 The RBBS-Verify Batch File..........................................19 The RBBS-Verify Configuration File..................................20 The VERIFIED.DAT Data File..........................................21 The TRASHCAN.DAT Data File..........................................22 The NUMBER.LOG File.................................................23 The VERIFYx.LOG File................................................24 The ERRORx.LOG File.................................................25 The SUCCESSV.x Door Information File................................26 The SUCCESSC.x Door Information File................................27 Table of Contents ───────────────── The LOGOFF/LOGOFFG Optional Display File............................28 The RBBSVRFY.KEY File...............................................29 Troubleshooting RBBS-Verify.........................................30 Troubleshooting RBBS-Verify (Continued).............................31 Support For RBBS-Verify.............................................32 RBBS-Verify Sysop Documentation Page: 1 Shareware Notice ──────────────── RBBS-Verify v1.00 has been released under the shareware concept, you are therefore granted a limited evaluation license to use this software on your own RBBS-PC system for a period of 30 days, after which you must either register the software, or discontinue it's use and remove the door from your system. RBBS-Verify is the result of over 8,000 total hours of development and deserves your support. RBBS-Verify may be freely distri- buted to all online services, bulletin board systems, user groups, share- ware distributors etc, as long as the software is distributed complete and in unmodified form. No fee may be charged for the enclosed software package. Shareware distributors may distribute RBBS-Verify on disk for a modest disk duplication and packaging charge not to exceed $6.00 per disk. Registered versions of RBBS-Verify must NEVER be distributed to ANYONE. Doing so violates U.S. and International copyright and trademark laws. Lightning Software will seek full criminal prosecution against violators. RBBS-Verify is a fully functional package when unregistered, however does have several limitations. The software however is not in anyway crippled, which means you can fully test the package, run it on your own system, and determine if the software meets your and your user's needs, then if you find that RBBS-Verify works for you, then you are required to register your copy if you wish to continue using the door. The registered version of the door does offer several additional features not included in the unregistered version, these are the VERIFIED.DAT and TRASHCAN.DAT data records, which will prevent duplicate phone numbers from being used again. The registered version also offers the NUMBER.LOG logging file for the Sysop, which can aid greatly in matching user names with phone numbers. Also included when you register RBBS-Verify is a 100% menu driven utility to help manage the RBBS-Verify online door and your RBBS-PC system, it is multitasker/network aware and is super easy to use, a bound printed manual, and lifetime support, not to mention the latest version of the software. As you can see from the above, registering RBBS-Verify offers tremendous benefits, you only need to register the door once, thereafter all future releases and upgrades are offered to you free of charge, plus when you register any Lightning Software product, you are given special pre-regist- ered access on our 24 hour a day/7 day a week support BBS. For complete details on registering your copy of RBBS-Verify, please read the included file ORDER.DOC. Thank you for choosing the RBBS-Verify door, we hope you find the software of value and will support the shareware concept by registering your copy today! RBBS-Verify Sysop Documentation Page: 2 Warranty ──────── RBBS-Verify 1.00 is distributed without warranty. In no event will Lightning Software be liable to you for any damages from running this program. Including any loss of profits, lost savings, or other incidental or consequential damages arising out of your use of or inability to use the program, even if Lightning Software or a authorized representative has been advised of the possibility of such damages. Lightning Software will not be liable for any such claim by any other party. All risk associated with using this program are the complete responsibility of the user. RBBS-Verify Sysop Documentation Page: 3 Acknowledgements ──────────────── RBBS-Verify v1.00 - Copyright (C) 1993 By Lightning Software, All Rights Reserved Worldwide. All products mentioned throughout the documentation for the RBBS-Verify online door are copyrights and/or registered trademarks of their respective authors/publishers. There has been tremendous response to the RBBS-Verify online door, and we would like to say a very special thanks to all of those who have contributed in one way or another to it's success. The RBBS-Verify online door represents our strong belief in the QuickBasic programmer's environment, we hope that it proves QuickBasic's abilities and will give others inspiration to use the language. RBBS-Verify's logic is very safe and reliable thanks to over 8 months of "tweaking". The tools used in the development of RBBS-Verify are what has made the door one of the best available, we would like to thank Todd Miller (creator of Door Source 4.0) for his wonderful library of door routines and for all of his support, Jeff Sumberg (creator of QBserial 3.0) for his superior serial I/O library and last but certainly not least Christy Gemmell (creator of The Assembly Language Toolbox for QuickBasic), one of the finest assembly language toolkits available. RBBS-Verify is written, coded, and debugged entirely in Microsoft QuickBasic 4.5 and utilizes the Door Source 4.0 library of door routines, the QBserial v3.0 interrupt driven serial I/O library and The Assembly Language Toolbox for QuickBasic. RBBS-Verify Sysop Documentation Page: 4 Introduction (Overview/Summary) ─────────────────────────────── Congratulations! You have selected the finest of RBBS-PC callback verification doors. RBBS-Verify is the perfect compliment to your RBBS system for both security and reliability needs. RBBS-Verify offers many features and customization options for the system operator. Listed below are only a few of RBBS-Verify's many quality features: - Complete multinode support. - Extremely easy installation and zero maintenance. - Supports baud rates up to 115,200 locked DTE using non-fossil routines! - Supports the use of a fossil driver however is not required. - Supports non-standard interrupt and IRQ's and communication ports 1-8. - Does not require the use of WatchDog or similar utilities. - Detects carrier loss and terminates cleanly if carrier is dropped. - Includes easy to use completely menu driven installation utility. - Fast high speed communication routines. - Fully supports all networks and multitasking software, a few include DesqView, Microsoft Windows, DoubleDOS, Lantastic, Novell and many more. - Colorful ANSI/non-ANSI graphics. - Fully Sysop configurable. - Supports local and long distance callback verification. * Features verification and trashcan records - will not allow same number to be verified again. * Features NUMBER.LOG - log file for the Sysop which lists the telephone number, user's name and date of verification for all caller's successfully verified. This information is vital for the Sysop, it's purposes greatly vary, however one of the most notable uses is to assist in locating/matching a user name with a phone number. - Supports an optional RBBS-PC callback statistic bulletin for your caller's to read. Logs successful and un-successful users who used the door. - Offers password security codes to protect you and your system. - Does not require the use of any run-time modules - all routines are handled internally. - Offers an extensive log for the Sysop - logs all user's who used the door, time, date, number dialed, whether security was raised, verify attempts successful and un-successful, plus much more. - Any program errors which occur are logged to a disk file for the Sysop. - Offers an optional callback mode so that user's may enter the door and have RBBS-Verify call them back to reverse the originating connection (normally helpful if the caller is experiencing a noisy phone line). - Built in macro code language ("@") support. - Offers built in - internal verification and callback instructions and allows the use of Sysop supplied instructions for both verification and callback mode. * = Requires registration to enable this feature RBBS-Verify Sysop Documentation Page: 5 Introduction (Overview/Summary) ─────────────────────────────── As you can see from above RBBS-Verify is one of the most full featured verification systems for RBBS-PC ever developed, and there are certainly more features than we can list here. We think after trying RBBS-Verify, you will agree - it is a one of a kind verification system offering both security and reliability. Please read this document carefully before installing the software for the first time. Thank you for choosing RBBS-Verify for your callback verification needs! RBBS-Verify Sysop Documentation Page: 6 Installing RBBS-Verify ────────────────────── RBBS-Verify has been designed to make installation of the software as simple as possible. To make the installation even easier, we have included a completely menu driven configuration setup utility. Please read through the following important installation instructions before attempting to use the software for the first time. [1.] Create a directory to hold all of the RBBS-Verify files, then decompress the RBBSV100.EXE archive into the above created directory. You may install RBBS-Verify into any directory you wish, in this documentation we will assume you have installed RBBS-Verify into the directory C:\RBBS\RBBSVRFY. [2.] Next, change to the above created directory and run the supplied INSTALL.BAT file. This file will run the RBBS-Verify configuration setup program, where you will decide how you want RBBS-Verify to be installed on your system. The following is the questions the setup utility will prompt you for. Please note when installing RBBS-Verify on a multinode RBBS system, you will need to create different configuration files for each node. Enter a configuration filename ------------------------------ This should be the current configuration filename you are installing. You may use any standard DOS filename you wish. For multinode systems, use a different config filename for each node, you might wish to use numbers if using multiple config files, such as RBBSV1.CFG for node 1, RBBSV2.CFG for node 2 and so on. Name of interface file (ie PCBOARD.SYS) --------------------------------------- This should be the full path and filename in ALL uppercase to your DORINFOx.DEF interface file (where x is the node number). Name of BBS ----------- Here enter your BBS's name EXACTLY the way you want RBBS-Verify to display it upon connection with a remote user, this will be used to display "This is ... calling for ...". Sysop's first name ------------------ Here enter the Sysop's first name (your name) as you are known to your caller's. Sysop's last name ----------------- Here enter the Sysop's last name (your name) as you are known to your caller's. RBBS-Verify Sysop Documentation Page: 7 Installing RBBS-Verify ────────────────────── Modem reset command - example ATZ --------------------------------- This should be the command needed to reinitialize your modem, for Hayes and compatible modems ATZ should work just fine, if you find that RBBS-Verify is unable to reset your modem, check your modems documentation for the correct command. Modem init string - example ATDT -------------------------------- This should be the initialization string you want sent to the modem when RBBS-Verify dials a remote user, this should be the dialing prefix you want to use, and any additional init commands to send to the modem. For touch tone dialing add DT to the end of the AT command, for pulse dialing add DP to the end of the AT command. You may add any additional commands you wish - such as turning the modems speaker on and off etc, however any additional commands you use MUST be entered before the dialing prefix (DT or DP). For Hayes and compatible modems ATDT should work just fine, if you find that RBBS-Verify is unable to dial the remote caller correctly check your modems documentation to find the correct commands. Allow long distance dialing (Y/N)? ---------------------------------- Enter a "Y" here if you want RBBS-Verify to make long distance calls, or enter a "N" if you do not want RBBS-Verify to call long distance. RBBS-Verify will automatically disconnect long distance caller's after successful verification. Security level of caller's to verify? ------------------------------------- This should be the security level of caller's to verify (normally the sec- urity level for new caller's), any user attempting to enter RBBS-Verify with a security level less than or greater than this security level will be entered into the door in callback only mode (if enabled), if the callback mode is disabled, the caller will simply be informed that their security level is either too high or too low for RBBS-Verify and will be rejected from the door and returned to the board. Security level to raise caller's to? ------------------------------------ This should be the security level you want RBBS-Verify to upgrade caller's to if they have been successful with callback verification. RBBS-Verify Sysop Documentation Page: 8 Installing RBBS-Verify ────────────────────── Path/filename of bulletin (N for none)? -------------------------------------- At this prompt, select whether you want RBBS-Verify to create a statistic bulletin. Entering an "N" at this prompt will not generate a statistic bulletin, however entering the path and filename of a bulletin here (without the graphic designator i.e: C or G) will cause RBBS-Verify to generate a statistic bulletin for your caller's to read. Path/filename of door information file? --------------------------------------- This should be the full path and filename of your door information file RBBS uses to receive information back from a door. RBBS usually uses this file in the main RBBS directory with a filename of DOUTx.DEF (where x is the node number). Enable callback mode (Y/N)? --------------------------- At this prompt select whether you wish to enable the callback mode of RBBS-Verify. If this option is enabled (by specifying a "Y") then any user attempting to enter the RBBS-Verify door with a security level less than or greater than the security level to verify (specified above) will enter the door in callback only mode, RBBS-Verify will then allow the user to have RBBS-Verify call them back to reverse the originating connection (normally helpful if the user is experiencing a noisy phone line), no security changes are made while in callback only mode. This option can be disabled by specifying a "N" at this prompt, any user attempting to enter RBBS-Verify with a security level less than or greater than the security level to verify (specified above) will be informed that their security is either too low or too high to use the RBBS-Verify door, they will then be rejected and returned to the board. Comm port to use (1/2 or base address)? --------------------------------------- Here you should enter the communication port RBBS-Verify will use, this value should be either 1 or 2 depending on which communication port you will be using (COM1 or COM2), enter ONLY the port number here, do NOT enter COM1. If you are running RBBS-Verify on a non-standard communication port, then you should enter the 3 character HEX base port address at this prompt. Refer to the table on page 14 of this guide for a listing of valid communication port address and IRQ levels. RBBS-Verify Sysop Documentation Page: 9 Installing RBBS-Verify ────────────────────── IRQ to use (1-15 or 0 if standard)? ----------------------------------- Here you should enter the communication port IRQ RBBS-Verify will use, this value should be set to 0 if you are using a standard communication port, otherwise you should enter the communication port IRQ you wish to use, this value can range from 1-15. Refer to the table on page 14 of this guide for a listing of valid communication port address and IRQ levels. Number of redial attempts (1-999)? ---------------------------------- This option should be set to the maximum number of times RBBS-Verify is to attempt to make connection with a remote caller, if RBBS-Verify is unable to make connection in one attempt, it will hang up and redial the caller again (up to this value). If this value is set to 1, RBBS-Verify will attempt only once to make connection with a caller. This value can range from 1 up to 999 times, the recommended setting is 3. Dialing delay factor to use? ---------------------------- This option requires a little explanation. This value is used to determine how many seconds to delay after RBBS-Verify dials a remote caller, this value is multiplied by 3. What this means, is that RBBS-Verify will delay a series of 3 times after it calls a user back and each time delaying this number of seconds while polling for carrier detection. So for example if this value was 10, RBBS-Verify would wait 30 seconds maximum after dialing a remote caller. RBBS-Verify uses this method to provide "quick-response" connect times, this allows the door to quickly determine if carrier from a remote modem is present, once the door sees that carrier detection is true, it continues execution with the "This is ... calling for ..." message. The recommended setting for this option for most modems is 10. Normally this value is always the best, however there is certain modems where a change to this value would become necessary, several high speed HST modems for example might require a change to this value. It is best to go with the recommended value of 10, however if you experience problems with RBBS-Verify hanging up too soon after calling a remote user back, then this value should be increased. RBBS-Verify Sysop Documentation Page: 10 Installing RBBS-Verify ────────────────────── Use internal verification instructions? --------------------------------------- RBBS-Verify supports the use of Sysop created instruction files, however the door also includes it's own built in door instructions, at this prompt you should select whether you wish to use RBBS-Verify's internal callback verification instructions, if you do, simply enter a "Y" to enable RBBS-Verify's built in instructions for use. If you prefer you may use your own custom door instructions by simply including the full path and filename of the instruction file you wish to use, this file should be in standard ASCII format, ANSI display files are not supported, however you can control several aspects of the display by using RBBS-Verify's built in macro language, these macros allow displaying the user's name, sending a bell to the user, changing display colors, etc. For a listing of the macro codes supported by RBBS-Verify, please refer to the included file MACRO.LST, included with RBBS-Verify v1.00. Use internal callback instructions? ----------------------------------- RBBS-Verify supports the use of Sysop created instruction files, however the door also includes it's own built in door instructions, at this prompt you should select whether you wish to use RBBS-Verify's internal callback mode instructions, if you do, simply enter a "Y" to enable RBBS- Verify's built in instructions for use. If you prefer you may use your own custom door instructions by simply including the full path and filename of the instruction file you wish to use, this file should be in standard ASCII format, ANSI display files are not supported, however you can control several aspects of the display by using RBBS-Verify's built in macro language, these macros allow displaying the user's name, sending a bell to the user, changing display colors, etc. For a listing of the macro codes supported by RBBS-Verify, please refer to the included file MACRO.LST, included with RBBS-Verify v1.00. IMPORTANT: Syntax examples above with included quotes i.e.: ("Y") are provided only for clarity, the configuration file should NOT contain any quotes. RBBS-Verify Sysop Documentation Page: 11 Installing RBBS-Verify ────────────────────── [3.] When you have completed entering configuration information, the next step is to create a batch file to run the door. The following is an example RBBS-Verify batch file used to run the door: ECHO OFF - Sets the DOS echo feature to off to prevent the commands from echoing to the screen. ECHO Loading RBBS-Verify Please Wait... >COM1 - Sends the caller a message to wait. CD\RBBS\RBBSVRFY - Changes to the directory containing all of the RBBS-Verify files. RBBSVRFY RBBSVRFY.CFG x. - Runs RBBS-Verify passing the full path and file- name of the configuration file plus the node number. CD\RBBS - Changes back to the RBBS directory. The above batch file is pretty straight forward, just remember where you see an x substitute x for the node number, edit the COM port number in line number 2 to reflect the correct communication port number. After completing all of the above steps, RBBS-Verify is completely setup and ready to run! So let's give it a try to be sure everything is working properly. Change to your directory containing the RBBS-Verify files, and enter the following command at the DOS prompt: RBBSVRFY RBBSVRFY.CFG LOCAL x Substitute your configuration filename above if different. Replace the x with the current node number. RBBS-Verify does not support local caller's, so after entering the above command RBBS-Verify should report such and return to DOS. If everything is well, you might wish to edit the TRASHCAN.DAT file (if you are running a registered copy of RBBS-Verify) to add your board's number to the list. TRASHCAN.DAT is a standard ASCII text file and can be edited using any standard ASCII text editor. Refer to the section titled "The TRASHCAN.DAT File" in this guide for details on the format used by this file. RBBS-Verify Sysop Documentation Page: 12 Files Included ────────────── The files included with the registered and unregistered versions of RBBS- Verify differ slightly, the following is a listing of the files you should have within the RBBSV100.EXE self extracting file, files which are included only with the unregistered version will have a "U" beside the filename. Files which are included only with the registered version will have a "R" beside the filename. All other files are included in both the unregistered and registered versions: RBBSVRFY.EXE - Main RBBS-Verify executable program. RBBSVRFY.CFG - Sample RBBS-Verify configuration file. RBBSVRFY.BAT - Sample RBBS-Verify batch file. RBBSVRFY.DOC - User's guide for the RBBS-Verify online door RBBSVRFY.KEY R RBBS-Verify registration key file. VERIFIED.DAT - Verified data file - stores all phone numbers verified successfully. TRASHCAN.DAT - Trashcan data file - stores invalid phone numbers. DOORINST.EXE - Door Installer - used to setup RBBS-Verify configuration files. RBBSVRFY.SET - Data file used by the Door Installer above. INSTALL.BAT - Installation batch file for RBBS-Verify. PATCH300.EXE - Patch to allow RBBS-Verify to operate at 300 baud. PATCH300.DOC - Documentation for the PATCH300.EXE program above. PATCHINF.EXE - Patch to correct user name bug in RBBS-Verify. PATCHINF.DOC - Documentation for the PATCHINF.EXE program above. MACROS.LST - Listing of RBBS-Verify's optional built in macro language commands. EDITDATA.EXE R Network/multinode aware utility to help manage your VERIFIED.DAT and TRASHCAN.DAT data files. EDITDATA.BGR R Overlay file used by the EDITDATA.EXE program above. EDITDATA.HLP R Help file used by the EDITDATA.EXE program above. EDITDATA.DOC R Documentation for the EDITDATA.EXE program above. ORDER.DOC U Registration form and instructions to register your copy of RBBS-Verify. MAILER.TXT U RBBS-Verify instant registration mailer. README.1ST - Important last minute information which was not included in this user's guide. FILE_ID.DIZ U Imbedded description file for RBBS-Verify. DESC.SDI U Imbedded description file for RBBS-Verify. If you are missing any of the above files which you should have, you may wish to contact our support BBS and download RBBS-Verify directly from us, see the "Support For RBBS-Verify" section in this guide for more information. RBBS-Verify Sysop Documentation Page: 13 Files Created During Run-Time ───────────────────────────── The following is a listing of files RBBS-Verify creates during normal run- time operation, and a brief description of each file. DOUTx.DEF - This file is created using the name and path specified in line 11 of the configuration file and is used to pass information back to RBBS-PC after successful verification. RBBS-PC *MUST* be able to locate this file! Note that x designates the node number. VERIFIED.DAT - If this file does not exist when RBBS-Verify is run, it will be created and initialized by the door. If you are running an unregistered version of the door, this file will be initialized but ignored thereafter. TRASHCAN.DAT - If this file does not exist when RBBS-Verify is run, it will be created and initialized by the door. If you are running an unregistered version of the door, this file will be initialized but ignored thereafter. NUMBER.LOG - This file will be created only after a caller has success- fully completed the callback verification process and only if you are running a registered version of the door. VERIFYx.LOG - If this file does not exist when RBBS-Verify is run, it will be created and initialized by the door. ERRORx.LOG - This file will be created by the door only in the event of a run-time error. SUCCESSV.x - This file will be created only after a caller has success- fully completed the callback verification process. SUCCESSC.x - This file will be created only after a caller has success- fully completed the callback process. NOTE: Detailed descriptions of most of the files above can be found in the RBBS-Verify file reference starting on page 18 of this guide. RBBS-Verify Sysop Documentation Page: 14 Optional Files Created During Operation ─────────────────────────────────────── If you specified a bulletin to be created in line number 10 of the config- uration file, then 3 versions of that file will be created. RBBS-Verify automatically adds the appropriate G or C to the end of the filename you specify, therefore make sure and DO NOT add either of these characters to the end of the filename. RBBS-Verify Sysop Documentation Page: 15 Optional Command Line Switches ────────────────────────────── RBBS-Verify provides many optional command line parameters to offer very flexible use, the following is a listing of the optional parameters that RBBS-Verify supports: LOCAL - Forces RBBS-Verify to run in local mode. This is really meant for RBBS-Verify's file initialization purposes, but it still reads the configuration file, but doesn't read the BBS interface file. Using this option will cause RBBS-Verify to re-create it's TRASHCAN.DAT, VERIFIED.DAT and VERIFYx.LOG files if any do not exist. NETWORK - Forces file sharing to be active in case you are using something other than SHARE to manage file locking. IRQ=n - Lets you change the IRQ used for the COM port specified in the BBS interface file. (See below for more information) ADDR=&Hnnnn - Lets you change the address used for the COM port specified in the BBS interface file. (See below for more information) PS2 - Forces the PS/2 IRQ's and addresses if a PS/2 isn't detected (normally it is, but you can't always tell!). The full command syntax for RBBS-Verify is as follows: RBBSVRFY <config file> [option] <node> Parameters shown inside <> brackets ARE REQUIRED, parameters shown inside [] brackets are optional and are shown above, these are not required for operation of the door. When you use the IRQ or the ADDR option, you must include the other. You can't use just the IRQ and not the ADDR, and you can't use just the ADDR and not the IRQ. Here's a chart with the STANDARD IRQ's and addresses for the PS/2's and IBM PC's: Non PS/2 COM Port IRQ Address 1 4 &H3F8 2 3 &H2F8 3 4 &H3E8 4 3 &H2E8 5-8 4 &H3F8 --------------------------------------------- PS/2 COM Port IRQ Address 1 4 &H3F8 2 3 &H2F8 3 3 &H3220 4 3 &H3228 5 3 &H4220 6 3 &H4228 7 3 &H5220 8 3 &H5228 RBBS-Verify Sysop Documentation Page: 16 Optional Command Line Switches ────────────────────────────── PLEASE NOTE: RBBS-Verify uses 2 different sets of parameters when using the door on non-standard communication ports, the address and IRQ level specified in the configuration file for the door is the same as the command line parameters, except you should NOT include the "&H" prefix (shown above) in the configuration file, for example when running RBBS-Verify on port 4 on the standard IBM PC, you should specify 2E8 as the HEX address in the configuration file, NOT &H2E8, however you would still specify the parameter ADDR=&H2E8 on the command line when invoking the door. The above address and IRQ information applies only if you plan to use RBBS-Verify on non-standard communication ports and interrupts. RBBS-Verify Sysop Documentation Page: 17 Sysop Function/ALT Keys ─────────────────────── RBBS-Verify offers many Sysop specific commands while a caller is in the door, these are as follows: F3 * Printer toggle F4 * Page bell toggle F5 - Shell to DOS F6 - Auto-disconnect caller F7 * Caller alarm toggle F8 - Return caller to board and notify caller F9 - Return caller to board and don't notify caller F10 - Start Sysop chat ESC - Enter/exit Sysop chat ALT-X * Drop to DOS after caller logs off ALT-N * Sysop next on flag Function keys with an "*" beside their description are not currently available in RBBS-Verify. These have been included for possible future additions in the door. Description of auto-disconnect ------------------------------ This is an extremely useful function offered by RBBS-Verify for the Sysop's use. There are 2 different ways to utilize this feature. RBBS-Verify allows the Sysop to create a file titled LOGOFF, and LOGOFFG, the first is a standard ASCII text file, and the other is a ANSI graphic file, if RBBS- Verify finds that these files are present, pressing the F6 key will cause RBBS-Verify to display the contents of the above file and disconnect the caller. If however the files do not exist, RBBS-Verify will simply disconnect the caller, in either case the caller is not notified by the door what is going on. RBBS-Verify will search for the existance of these optional display files and will display whichever one it finds first based on the current user's graphic selection. You should also note that all of RBBS-Verify's optional macro language codes may be used with these display files. RBBS-Verify Sysop Documentation Page: 18 Using RBBS-Verify on Non-RBBS Systems ───────────────────────────────────── RBBS-Verify should run on any system that is capable of generating a DORINFOx.DEF format interface file however, RBBS-Verify will not be able to raise a user's security level on a non-RBBS-PC system. If you wish to use RBBS-Verify to it's full capability on a non-RBBS system, you will need to seek a good conversion utility capable of creating a RBBS com- patible DOUTx.DEF door information file. RBBS-Verify Sysop Documentation Page: 19 The RBBS-Verify Batch File ────────────────────────── The following is the format of the RBBS-Verify batch file, this is simply an example - you may add/change/delete anything you wish, this example will hopefully also help those user's who are not familiar with creating batch files for online doors: ECHO OFF - Sets the DOS echo feature to off to prevent the commands from echoing to the screen. ECHO Loading RBBS-Verify Please Wait... >COM1 - Sends the caller a message to wait. CD\RBBS\RBBSVRFY - Changes to the directory containing all of the RBBS-Verify files. RBBSVRFY RBBSVRFY.CFG x. - Runs RBBS-Verify passing the full path and file- name of the configuration file plus the node number. CD\RBBS - Changes back to the RBBS directory. RBBS-Verify Sysop Documentation Page: 20 The RBBS-Verify Configuration File ────────────────────────────────── The following is the format of the RBBS-Verify configuration file, if for some reason you need to edit the configuration file using something other than DOORINST.EXE, this example should help familiarize you with the format used by the configuration file. All lines ARE REQUIRED! THERE SHOULD BE NO BLANK LINES IN THE CONFIG FILE!!! C:\RBBS\DORINFO1.DEF - Full path/filename of DORINFOx.DEF file (IN ALL UPPERCASE!) Software Express - Your BBS name Jerry - The Sysop's first name Highland - The Sysop's last name ATZ - Modem reset command ATDT - Modem initialization string N - Allow long distance caller's (Y=Yes N=No) 10 - Security level to verify (normally new user access level) 20 - Security level to raise successful caller's to C:\RBBS\BULLETIN\BULLET1 - Path/filename of optional statistic bulletin (N for none) - without graphic designator C:\RBBS\DOUT1.DEF - Path/filename of RBBS-PC door information file (normally DOUTx.DEF where x is the node number) Y - Enable callback mode (Y=Yes N=No) 1 - Communication port to use (1/2 or base address) 0 - Communication port IRQ to use (1-15 or 0 if standard) 3 - Number of redial attempts (1 to 999) 10 - Dialing delay factor to use (10 is recommended for most modems) Y - Use internal verification instructions (Y or path/filename of instruction file to use) Y - Use internal callback instructions (Y or path/filename of instruction file to use) The remainder of the configuration file is ignored by RBBS-Verify and may be used freely for any comments you might wish to add. RBBS-Verify Sysop Documentation Page: 21 The VERIFIED.DAT Data File ────────────────────────── RBBS-Verify uses the VERIFIED.DAT file to hold all of the phone numbers of user's who have been successfully verified. This file is a standard ASCII text file and can be edited using any standard ASCII text editor. The format of the VERIFIED.DAT file is: 000-000-0000 - each line should contain the full phone number (including area code) with the separators in place i.e: (-). PLEASE NOTE: The file above is used only in the registered version of RBBS-Verify - it will be created and initialized but thereafter ignored in the unregistered version. Editing this file incorrectly can cause MAJOR problems, since each record is in a fixed length format. Registered user's may find it easier (and safer) to edit the file using the included EDITDATA.EXE utility, see the file EDITDATA.DOC for instructions. RBBS-Verify Sysop Documentation Page: 22 The TRASHCAN.DAT Data File ────────────────────────── RBBS-Verify uses the TRASHCAN.DAT file to hold all of the phone numbers which the Sysop does not want dialed. This file is a standard ASCII text file and can be edited using any standard ASCII text editor. The format of the TRASHCAN.DAT file is: 000-000-0000 - each line should contain the full phone number (including area code) with the separators in place i.e: (-). PLEASE NOTE: The file above is used only in the registered version of RBBS-Verify - it will be created and initialized but thereafter ignored in the unregistered version. Editing this file incorrectly can cause MAJOR problems, since each record is in a fixed length format. Registered user's may find it easier (and safer) to edit the file using the included EDITDATA.EXE utility, see the file EDITDATA.DOC for instructions. RBBS-Verify Sysop Documentation Page: 23 The NUMBER.LOG File ─────────────────── The NUMBER.LOG file is a standard ASCII text file and is used to hold the user's telephone number, name and the date of verification, this file is created just after a caller has been successfully verified and is provided as a general log file for the Sysop, it can be used for many different purposes, however, the most notable is allowing the Sysop to match tele- phone numbers with a user's name, which can assist greatly in locating duplicate user names. This file is separate from the VERIFYx.LOG file since the size of the VERIFYx.LOG file can at times get quite large requiring deletion, this file remains relatively small. PLEASE NOTE: This file is used only in the registered version of RBBS-Verify - it will be ignored in the unregistered version. RBBS-Verify Sysop Documentation Page: 24 The VERIFYx.LOG File ──────────────────── The VERIFYx.LOG file is a standard ASCII text file which is used to log all of the doors activities, such useful logging features includes, who and at what time and date entered the door, the number RBBS-Verify dialed the user at, plus many more functions and activities are logged, this file is designed to be an extensive log for the Sysop. Note that x indicates the node number. RBBS-Verify Sysop Documentation Page: 25 The ERRORx.LOG File ─────────────────── The ERRORx.LOG file is a standard ASCII text file which is used to log all of the run-time errors which occurred during the operation of RBBS-Verify, this file lists the run-time error, the error number that occurred and at what time and on what date the error occurred. If you have trouble with RBBS-Verify, check this file for the error number, if you are unable to resolve the trouble, have this error number handy and contact us for support. RBBS-Verify Sysop Documentation Page: 26 The SUCCESSV.x Door Information File ──────────────────────────────────── The SUCCESSV.x file is provided as a means for RBBS-Verify to transfer data to and from another application. Where the x indicates the node number. This was provided to encourage third party software development for the RBBS-Verify door, this file will be created when a user has been success- fully verified, each line contains useful information which is necessary for a door or utility author who wishes to write external applications for use in conjunction with RBBS-Verify, the file is a standard ASCII text file and consists of the following information: **** Verification successful **** - Header message Jerry Highland - The user's full name Lithia Springs, Ga - The user's location 24 - The user's time left on the system 20 - The user's NEW security level 2 - The user's graphics selection (0=No graphics/1=ASCII/2=ANSI color) When utilizing this file - please note that RBBS-Verify does NOT delete this file each time the door is run, it simply re-writes the file again. This file is ONLY updated and re-written when a caller has been successful with the verification process. RBBS-Verify Sysop Documentation Page: 27 The SUCCESSC.x Door Information File ──────────────────────────────────── The SUCCESSC.x file is provided as a means for RBBS-Verify to transfer data to and from another application. Where the x indicates the node number. This was provided to encourage third party software development for the RBBS-Verify door, this file will be created when a user has successfully completed the callback process (this is assuming the callback mode is enabled), each line contains useful information which is necessary for a door or utility author who wishes to write external applications for use in conjunction with RBBS-Verify, this file is a standard ASCII text file and consists of the following information: **** Callback successful **** - Header message Jerry Highland - The user's full name Lithia Springs, Ga - The user's location 24 - The user's time left on the system 20 - The user's CURRENT security level 2 - The user's graphics selection (0=No graphics/1=ASCII/2=ANSI color) When utilizing this file - please note that RBBS-Verify does NOT delete this file each time the door is run, it simply re-writes the file again. This file is ONLY updated and re-written when a caller has been successful with the callback process. RBBS-Verify Sysop Documentation Page: 28 The LOGOFF/LOGOFFG Optional Display File ──────────────────────────────────────── The 2 files LOGOFF and LOGOFFG are both optional display files you may wish to create, they are used in conjunction with RBBS-Verify's F6 (auto- disconnect) function key. LOGOFF is a standard ASCII text display file and LOGOFFG is a ANSI color display file. They are both optional files, if these files do not exist, pressing the F6 function key simply disconnects the current user. If however these files do exist, pressing the F6 function key will display the file LOGOFF if the user is in non-graphic mode or LOGOFFG if the user is in ANSI color mode and disconnect the caller, experiment with using this feature, and be creative! This option is useful for problem caller's. Either way you wish to implement this feature - RBBS- Verify will never inform the caller of anything. RBBS-Verify will search for the existance of these optional display files and will display which- ever one it finds first based on the current user's graphic selection. You should also note that all of RBBS-Verify's optional macro language codes may be used with these display files. RBBS-Verify Sysop Documentation Page: 29 The RBBSVRFY.KEY File ───────────────────── When you register RBBS-Verify you will receive a registration key file re- gistered in your board's name, this key file will be used to register the software and enable several additional features of the door. To install your key file, all that is necessary is to simply copy the file into the directory holding all of your RBBS-Verify files. It's a good idea to make a backup of this file, since there will be only ONE to go around. Then place the backup in a safe place. RBBS-Verify Sysop Documentation Page: 30 Troubleshooting RBBS-Verify ─────────────────────────── This section is designed to isolate most of the common problems user's may experience while operating the RBBS-Verify online door. Hopefully in the event of a problem, this section will be of some help, if after going over this section you are still unable to resolve the problem, please refer to the "Support For RBBS-Verify" section in this guide. (P) = Problem (S) = Solution (P) - RBBS-Verify reports to the caller "File not found - report to Sysop!". (S) - This indicates that RBBS-Verify tried to open it's user supplied door instructions, however the file was not found. Make sure that the path and filename to the file has been specified correctly in the configuration file and the file actually exists. Although not required it is strongly recommended that you place all of RBBS- Verify's files the door uses within it's own directory, this provides clarity. (P) - Receive message "Error xx opening comm port" while trying to run RBBS-Verify. (S) - This error indicates there was an error while trying to open and initialize the communication port, this error is normally due to an invalid communication port or baud rate being passed to the door from the door interface file. If you are using the door on a non- standard communication port - this error can also indicate an illegal port address or IRQ level. Check these parameters carefully to insure all information is correct. Please also note that this error can occur when trying to operate RBBS-Verify in local mode from RBBS, this is due to RBBS not passing a valid baud rate to doors in local mode. RBBS-Verify does not support local logons anyway however, if you have trouble running some doors in local mode, we have a patch program available which will patch the door interface file to run with most doors in local mode, this patch is available on our support board (Software Express) under the filename of PATCHLCL.ZIP. Note that this patch is not needed for RBBS-Verify. RBBS-Verify Sysop Documentation Page: 31 Troubleshooting RBBS-Verify ─────────────────────────── (P) - BBS calls door and returns to the board. (S) - Check your configuration file to be sure all information has been entered correctly, also make sure that the full path and filename of your DORINFOx.DEF interface file has been entered in ALL uppercase, do NOT use lowercase! If this is correct, recheck all batch files used to run the door, normally it's something very simple. (P) - RBBS-Verify displays fatal error message. (S) - This error can mean many, many things, this is RBBS-Verify's way of preventing the entire door from going down, by terminating cleanly and exiting back to the board. This error message occurs when it is un-safe for RBBS-Verify to continue, when you receive this error message, view the log file RBBS-Verify creates ERRORx.LOG (where x is the node number), this file contains the run-time error that occurred and the date and time, these error codes indicate QuickBasic's standard errors, check to be sure all information in the config and batch files have been entered correctly, ensure all files are where they should be and try the door again, if you are unable to correct the trouble, see the "Support For RBBS-Verify" section in this guide, write this error code down, you will need it when writing or calling for support. Hopefully the above listed problems and solutions will help you correct any problem you are having with the RBBS-Verify online door, if not we would be glad to assist you, please read the "Support For RBBS-Verify" section in this guide. RBBS-Verify Sysop Documentation Page: 32 Support For RBBS-Verify ─────────────────────── Support may be obtained 24 hours a day, 7 days a week for the RBBS-Verify online door on the Lightning Software support BBS (Software Express) at (404) 941-2822. The latest version of RBBS-Verify plus all of our other quality software products may be obtained on our support BBS. We would appreciate any comments/suggestions or future enhancements you might have, we would be glad to hear from you! Support is also available by writing to us at the following address: Lightning Software P.O. Box 177 Lithia Springs, Ga 30057